home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
doors_1
/
mezz431.zip
/
MEZANINE.DOC
< prev
next >
Wrap
Text File
|
1993-01-20
|
74KB
|
1,619 lines
METRO-MEZZANINE, Type IV
Version 4.31
By Steven H. Lin
Copyright 1992 by Steven H. Lin
All rights reserved
GENERAL OPERATIONS MANUAL
-----------------------------------------------------------------------------
CONTENTS
1.0 Introduction
2.0 Registration
3.0 The Purpose of Metro-Mezzanine
4.0 Requirements
5.0 Installation
6.0 Setup
7.0 Task Management
8.0 Product Support
9.0 Acknowledgements
10.0 Final Words
11.0 Registration Form
-----------------------------------------------------------------------------
1.0 INTRODUCTION
If you are a BBS aficionado type of system operator (sysop), then
Metro-Mezzanine may be for you. Testing more than one BBS program at a time,
or just running your usual one while testing another for whatever reason,
can be time- and space-consuming as you struggle with rearranging your hard
disk and other facets of your system to accomodate each BBS program as much
as you can without adversely affecting the others.
Metro-Mezzanine can help, by making access to the different BBS programs (or
even to just ONE, if you need a special customizable front-end program
between your mailer and your BBS) as painless as possible. In this age of
sophistication, making things more palatable is a definite plus.
1.1 Warning -
If you have never used a program from [The Deviant's Palace], then
you may be in for a massive shock. Please, if you suffer from an
angina pectoris condition, keep your supply of amyl nitrate or
nitroglycerin within easy reach. If you are using stronger
medications, like calcium channel blocking agents (most notably
verapamil) or ß-adrenoceptor blocking agents (AKA "beta blockers"),
you may want to have some experienced medical personnel nearby to
monitor your health condition as you set up Metro-Mezzanine. Use
Metro-Mezzanine at your own risk.
If you suffer from psychological problems or disabilities,
Metro-Mezzanine is not guaranteed to not injury your psyche. Use
Metro-Mezzanine at your own risk.
1.2 License Agreement -
The author of Metro-Mezzanine has taken every precaution to insure
that no harm or damage will occur on computer systems operating the
Metro-Mezzanine package. Nevertheless, the author of Metro-Mezzanine
shall NOT be held liable for whatever may happen on your computer
system or to any computer systems which connect to your own as a
result of operating the Metro-Mezzanine package. The user assumes
full responsibility for the correct operation of this software
package, whether harm or damage results from software error,
hardware malfunction, or operator error. NO warranties are offered,
expressly stated or implied, including without limitation or
restriction any warranties of operation for a particular purpose
and/or merchantability.
The Metro-Mezzanine main program, setup program, and documentation
are copyrighted products of Steven H. Lin. Steven H. Lin reserves
all rights to these products. This is protected by the United States
of America (USA) and International Copyright Laws. In no way shall
the components of the Metro-Mezzanine software package be reproduced
or modified in any form or method without prior expressly written
permission from Steven H. Lin.
Steven H. Lin grants an unlimited license for the purpose of dis-
tributing unregistered copies of the Metro-Mezzanine software
package to the public when such unregistered copies are released
from [The Deviant's Palace]. Tampering with or altering the contents
or integrity of the Metro-Mezzanine software package is prohibited.
No fee may be charged by any agency other than Steven H. Lin beyond
cost of distributing unregistered copies without prior expressly
written permission from Steven H. Lin.
Metro-Mezzanine is distributed under the Shareware concept. You are
allowed to operate Metro-Mezzanine for a trial period of thirty (30)
days. After this trial period, you must register Metro-Mezzanine or
discontinue its usage. Continued operation of Metro-Mezzanine past
the above stated trial period requires full registration payment.
The transfer of copyright ownership of Metro-Mezzanine from DevPal
MetroNet Communications, Inc. to the author of Metro-Mezzanine,
Steven H. Lin, does not in any way change the license agreement
explained above.
1.3 The New and the Old -
For newbies (AKA people who are using Metro-Mezzanine for the first
time), Metro-Mezzanine will be a brand-new experience, something
which is not too difficult to set up, particularly managing the
interface between your choice of BBS front-end/mailer, Metro-
Mezzanine, and your BBS programs.
On the other hand, for the oldsies (AKA people who have used
previous Types of Metro-Mezzanine (ie. Types I, II, and III)),
reading this document will be a GREAT help, especially for those who
are less inclined to "fool around and figure things out" for
themselves. Anyway, even these more technically-oriented people will
have some difficulty in figuring out the method to the madness that
Metro-Mezzanine's programmer exhibits.
The reason for this is simple: although superficially, many of
Metro-Mezzanine's features are very familiar to the oldsies, the
fundamental design of Metro-Mezzanine was radically changed (some
might even consider it to be greatly improved!). There was an
attempt to keep as many items familiar to the oldsies as possible to
reduce the confusion in the upgrade process; however, some of the
new features and options could not be reconciled with the old
design, for obvious reasons (which you oldsies will see).
-----------------------------------------------------------------------------
2.0 REGISTRATION
Registration of Metro-Mezzanine is mandatory if you wish to continue using
Metro-Mezzanine past the thirty-day trial period.
The unregistered demo mode of Metro-Mezzanine is fully functional, but it
does NOT have the bonus features which are available to registered sysops to
further enhance the performance and versatility of Metro-Mezzanine. To put it
in another light, the unregistered demo mode has the necessary basic con-
figuration for Metro-Mezzanine, while the registered mode possesses the
full-blown maximally-expanded configuration.
Many of the features mentioned in this text will apply only to the registered
version; when running the unregistered demo, it will become obvious which
capabilities are not included in the basic package. This document will, thus,
still be very useful when you register your product; it is highly recommended
that you have this document formatted and printed out nicely so that you will
have a permanent reference source readily available to you when needed.
There are different registration plans available, depending upon which
category your system falls into:
Non-Commercial System
Commercial System
System with Registered DevOnline Product(s)
After reading sections 2.1 - 2.4, complete the registration form at the
end of this document.
Issue a check or money order to STEVEN H. LIN.
Send the registration form and the check or money order to:
Steven H. Lin
DevPal MetroNet Communications
1251 NE 108th Street, #621
Miami, Florida 33161
United States of America
2.1 Instructions for Non-Commercial Systems -
To be considered a "non-commercial system", your system must be
physically located in a private residence and NOT be engaged in
commercial activities. These commercial activities include, but are
not limited to:
Subscription/registration REQUIRED for system access
Subscription/registration REQUIRED for access to a
part of the system
Product support for a product written or marketed by
the system operator(s) engaged in running, or aiding
in running, the system.
Product support for materials which the system operator(s)
have agreed to manage for the authors of those materials.
This includes ASP distribution sites.
The registration fees for a non-commercial system are:
$20.00 US
2.2 Instructions for Commercial Systems -
To be considered a "commercial system", your system must be
physically located in a non-private residence OR be engaged in
commercial activities. These commercial activities include, but
are not limited to:
Subscription/registration REQUIRED for system access
Subscription/registration REQUIRED for access to a
part of the system
Product support for a product written or marketed by
the system operator(s) engaged in running, or aiding
in running, the system.
Product support for materials which the system operator(s)
have agreed to manage for the authors of those materials.
This includes ASP distribution sites.
The registration fee for a commercial system is:
$35.00 US
2.3 Instructions for Systems with Registered DevOnline(tm) Products -
The limited-time discount offer program previously available
to individuals who have registered other DevOnline products has
concluded; this payment option is no longer in effect, as of the
first public release of Metro-Mezzanine Type IV. If you are
registering Metro-Mezzanine, check to make sure that you are
either registering under the commercial or non-commercial plans
listed in Sections 2.1 and 2.2.
2.4 Additional Costs -
In addition to registration of Metro-Mezzanine, there may be other
costs, depending on the method of delivery that you choose.
Delivery of registration key via FidoNet NetMail: FREE
Download of registration key from DevPalMiami : FREE
Complete registered version sent via USPS mail : $5.00 US
If you decide upon downloading the registration key from
DevPalMiami, remember to provide a filename and a security password
for the archive in which your key will be placed.
If you wish to access [The Deviant's Palace] at Miami computer system
metronetwork (AKA DevPalMiami), there are currently three accounts
available to DevOnline product registrants:
Basic status: 30-45 minutes per day
Regular status: 60 minutes per day
Executive/Preferred: 120 minutes per day
Each of the accounts have above-average downloading privileges, but
the Executive/Preferred account has by far the most lenient. All
subscription rates are discounted from their standard rates, so that
DevOnline registrants may take advantage of many of the special and
unique features at DevPalMiami.
-----------------------------------------------------------------------------
3.0 THE PURPOSE OF METRO-MEZZANINE
Metro-Mezzanine is a BBS carousel, in the tradition of Ghostwheel, the
earliest ever produced. Metro-Mezzanine's history is long and involved,
but it essentially begins with Ghostwheel, from which the Matrix login
method was adapted and also from which simple analogs were made by others.
Now the development cycle comes full circle, as Ghostwheel is now resurrected
for widespread use in the form of Metro-Mezzanine. Why settle for a poor
shade of Ghostwheel when you can have THE successor to Ghostwheel?
But what is a BBS carousel? Whenever a sysop decides that operating more
than one BBS program is necessary (perhaps by joining different BBS programs
with different strengths together, the end effect is much greater than the
sum of the total, or perhaps more security is required than can be supplied
by one BBS program, or perhaps the sysop just wants to test out a new BBS
program with his enterprising users without having to drop his existing BBS
package and the users who wish to enjoy the status quo), a BBS carousel is a
logical solution. This is a program which allows the sysop to offer his users
the choice to access any of a number of BBS programs that are running on his
system, in a metronet-like fashion.
In addition, Metro-Mezzanine has other features which will aid the sysop in
directing his users:
An easy-to-use menu construction system, comparable to (but
simpler than) the TBBS/QuickBBS/RemoteAccess menu language.
The ability to display text files as well as jump to different
BBS programs, individually and in tandem. Also, the ability to
offer an easy-to-maintain bulletin selection menu system if so
desired.
The flexibility of errorlevels to initiate access to each
BBS program.
The ability to offer downloading of files specified by the sysop
for his users via Omen Technology's DSZ protocol subsystem.
3.1 Greater Utility in This Age of Technology -
The initial release of Metro-Mezzanine was never intended to make as
great an impact as it has. Unbeknownst to the author, there are
substantially more people eager for a BBS carousel than originally
estimated, by at least 580%. A major impact Metro-Mezzanine has made
is on systems operating within more than one mail network: the use of
Metro-Mezzanine to allow access to multiple BBS partitions, with
each partition operating within a different mail network, is
tremendously popular. DevPalMiami itself is able to operate within
several mail networks using different technologies (FidoNet, QWK,
ExecNet, and VBBS methods) because of Metro-Mezzanine. This
incredible expansion of connectivity and configurability frees
sysops from needing all sorts of ugly, kludgy methods of trying to
tie together different technologies and lets them concentrate on the
important aspects of running a colorful, diversified system. If you
want to operate your system within more than one mail network, then
Metro-Mezzanine is an excellent option for you.
3.1.1 "Take two!" (4 December 1992) -
Well, it has been several months since I made the statement
in Section 3.1. Here is an update:
Interest in Metro-Mezzanine has continued to grow
exponentially as new BBS products, such as more versatile
BBS programs and graphics-oriented BBS programs and new mail
networking technologies and many other new developments,
keep appearing on the Modemland scene.
Because of this, Metro-Mezzanine is taking on more and more
innovative features to accomodate everybody's needs.
However, I realize that there are many features that I have
not even thought of, which could be introduced into
Metro-Mezzanine or provided as an add-on module to
Metro-Mezzanine. If you have any ideas on how to improve
Metro-Mezzanine's usefulness to Modemland, feel free to let
me know.
At this point, improving Metro-Mezzanine will be helping
literally THOUSANDS of BBS sysops worldwide. Help us to help
yourself and the grateful masses.
Thanks. - S/L
-----------------------------------------------------------------------------
4.0 REQUIREMENTS
4.1 General System Requirements -
The following are the requirements for using Metro-Mezzanine:
An MS-DOS computer
A modem
At least one BBS program or telecommunications host package
A front-end/mailer (eg. FrontDoor, BinkleyTerm)
An ANSI driver
At least 250Kb of hard disk space...
(can be run from floppy, but what about the BBS's?)
As much RAM as needed for the most memory-requiring of the
BBS programs or telecommunications host packages used
4.2 Environments -
Metro-Mezzanine will work under the following environments (although
it is certainly not limited to only the following):
Artisoft LANtastic 3.3 - 4.1
Compaq MS-DOS 3.31
Digital Research DR-DOS 5.0 - 6.0
Microsoft MS-DOS 3.3 - 5.0
Quarterdeck DesqView 2.31 - 2.42
4.3 Memory Managers -
Metro-Mezzanine appears well-behaved when operating under memory
management programs, such as 386-to-the-Max, HIMEM, QEMM-386, and
NetRoom. This is primarily because Metro-Mezzanine does not perform
any unusual operations in high memory areas (ie. extended memory,
expanded memory). It is also strongly advised that Metro-Mezzanine
NOT be loaded into any high memory areas.
-----------------------------------------------------------------------------
5.0 INSTALLATION
Installation is fairly simple.
Make a directory somewhere for the placement of Metro-Mezzanine.
Then unZIP the archive into that directory.
At this point, you will have a batch file called INSTALL.BAT in your
directory. Run it, and it will go ahead and establish some directories
needed by Metro-Mezzanine and break out some files from a self-extracting
archive.
Now you are finished with the installation of the program.
5.1 READ.ME -
It is a very good idea to read the READ.ME file to make sure that
you have not missed any important notes or comments concerning the
version of Metro-Mezzanine you are using.
5.2 Upgrading from Older Versions of Metro-Mezzanine -
Type IV is so radically different from previous Types that you will
not be able to upgrade your Metro-Mezzanine setup. You will have to
start anew.
-----------------------------------------------------------------------------
6.0 SETUP
Setup involves several steps:
Running the Metro-Mezzanine setup program (MEZSETUP) to initialize
the needed data files and to accept your choices for access in
Metro-Mezzanine.
Setting up your BBS batch file to handle Metro-Mezzanine.
Modifying DOOR information files to handle incoming callers.
6.1 The Metro-Mezzanine Setup Program -
In your Metro-Mezzanine directory, there is a program called
MEZSETUP.EXE. To run it, type the following at your DOS command
prompt:
MEZSETUP
You will be given a screen display announcing the program, then you
will asked to hit <ENTER>, whereupon you will be presented with the
main MezSetup menu.
Metro-Mezzanine Type IV has a few options at the main menu of its
setup program, and they are arranged as follows:
MezSetup 4.12 (12/03/1992)
---------------------------------------------------------
[A] Create/Edit/Delete Tasks
[B] Set Welcome/Intro Task
[C] Set Initial Menu Task
[D] Set Default Command Prompt
[E] Set Protocol Menu Name
[F] Set Registration Screen Display
[G] Set Excessive C/R Limit
[?] Show Status of Filenames
[Q]UIT MezSetup
[MezSetup]:
At the prompt, you may enter the option you wish.
6.1.1 The impropriety of NOT registering Metro-Mezzanine -
The unregistered Metro-Mezzanine does not offer all of the
fringe benefits shown in the screen above. The unregistered
Metro-Mezzanine works as a simple yet efficient BBS
carousel. There is no need to worry about all sorts of
confusing options that registered users have to contend
with. The following descriptions of the features within
MezSetup that are available in the registered version are
marked with the "{+}" symbol. Please make a note of them.
On the other hand, the registered Metro-Mezzanine is
jam-packed with many useful extra features that enable any
creative user the ability to transform Metro-Mezzanine into
an expression of his or her own conception of a BBS
metronetwork.
6.1.2 Create/Edit/Delete Tasks -
This is the heart of the Metro-Mezzanine setup process. The
term "Task" is used to refer to what was once known as a
"Partition": that is, Tasks are what constitute all of the
activities which can be performed within Metro-Mezzanine. It
may be a command to access a BBS program or a utility; it
may be a command to display a text file; it may even be a
command to download a file to the user.
This command allows you to provide Metro-Mezzanine with the
necessary options so that your users may perform whatever
functions you wish to allow them in the BBS carousel.
Metro-Mezzanine stores all of its Task data files (these are
files with the .TSK file extension) in the DATA subdirectory
(which was created during the installation process earlier).
Metro-Mezzanine starts with a couple of pre-named Tasks.
These are the WELCOME and MAIN Tasks. They are blank: that
is, although they exist, -you- need to fill in the
appropriate information to make them do what you need them
to do.
When you access this command, you will see a list of current
Tasks in the DATA subdirectory. Hence, you should see both
WELCOME.TSK and MAIN.TSK listed.
The screen will look something like this:
Current list of Tasks:
WELCOME.TSK - NONE [type 0]
MAIN.TSK - NONE [type 0]
[A]dd Task / [E]dit Task / [D]elete Task / [Q]uit
(>
From this new prompt (that thing on the screen that looks
like "(>"), you can choose one of four options, three of
which will help you manage the Tasks on your system.
6.1.2.1 Add Task -
This allows you to create new Tasks. This option
will first ask you for an eight-character filename
for the Task (you might have guessed by now that
MezSetup will automatically label all Task files
with the file suffix of .TSK). After you enter in
your filename, it will allow you to edit the
features required to make up a Task. Again,
unregistered users are unburdened by all of the
complex extra options available to registered
users.
Consult Section 7.0 for detailed instructions con-
cerning Task management.
6.1.2.2 Edit Task -
This allows you to edit existing Tasks. It will
first ask you for the filename of the Task you
desire to edit (excluding the .TSK suffix, of
course). Then, it will present you with a palette of
all of the features in a Task that you can edit.
Again, unregistered users are unburdened by all of
the complex extra options available to registered
users.
Consult Section 7.0 for detailed instructions con-
cerning Task management.
6.1.2.3 Delete Task -
This allows you to delete existing Tasks. Although
you may certainly delete Task data files from your
DOS prompt, you can also delete them from within
MezSetup, thus negating the need to constantly jump
out of MezSetup and then back in during those long
marathon sessions of changing or adding features to
your Metro-Mezzanine setup.
This option asks you for the filename,
excluding the .TSK suffix, of the Task you wish to
delete. And then, <whooosh!>, the Task is deleted.
6.1.3 Set Welcome/Intro Task {+} -
Default: "WELCOME"
As mentioned in Section 6.1.2, there is a WELCOME Task
already in existence when Metro-Mezzanine is first set up.
This is set up as the default Welcome/Intro Task for
Metro-Mezzanine. The filename is not alterable by
unregistered users, but it CAN be changed if desired by
registered users.
Selecting this option will allow you to enter in the
name of the Task that you wish to be run as the FIRST Task
presented to incoming callers.
The Welcome/Intro Task is typically a text file
display of your choice, but you can make it into one of the
other Task Types (see Section 7.0) if desired.
6.1.4 Set Initial Menu Task {+} -
Default: "MAIN"
As mentioned in Section 6.1.2, there is a MAIN Task already
in existence when Metro-Mezzanine is first set up. This is
set up as the default Initial Menu Task for Metro-Mezzanine.
The filename is not alterable by unregistered users, but it
CAN be changed if desired by registered users.
Selecting this option will allow you to enter in the
name of the Task that you wish to be run as the FIRST Menu
Task presented to incoming callers. See Section 7.0 for
information concerning Menu Tasks.
6.1.5 Set Default Command Prompt {+} -
Default: "[M-M IV]:"
In case you omit a configured command prompt design in any
of your Tasks, this is a default which will be displayed. It
is a good idea to make this pertinent to your system.
6.1.6 Set Protocol Menu Name {+} -
Default: "PROTOCOL"
This is the text file display shown to users explaining the
transfer protocols available for downloading files.
6.1.7 Set Registration Screen Display {+} -
Ever get tired of that registration information at the
beginning of every Metro-Mezzanine run? This option will let
you change it! When you access this option, you will be
presented with a short menu, allowing you to pick the type
of registration screen you'd like to present to the world.
There are three settings for the registration screen MODE:
0 - standard
1 - abbreviated
2 - customized
Let's explore each of these settings...
Type 0 is the default, and it is the same "boring"
registration information that has been displayed ever since
Type I (with changes to make it fit Type II, of course).
Type 1 is just a one-line description line, identifying the
program (Metro-Mezzanine), the program version, and the
program's last compilation date. This is very convenient for
the sysop who wants a no-nonsense presentation to his users.
Type 2 allows for you to make your own registration
information screen for Metro-Mezzanine. If you input "2" as
your setting, another option will appear in the menu for
this section: filename for the registration screen. It is
set to a default of "REGINFO.ASC". You may change the
filename to fit your personal tastes. Note that this screen
should preferably be in ASCII, in case some of your users do
not have ANSI capabilities or prefer NOT to see your
registration information screen in ANSI.
6.1.8 Set Excessive C/R Limit {+} -
Sometimes some users derive immense joy from whacking the
<ENTER> key excessively. While this is great fun for them,
it may be annoying to you, especially if you happen to pass
by and notice the ridiculous tomfoolery on your monitors.
What may be worse is that it could be due NOT to the user's
antics but a real connection problem. Rather than agonize
over this, you can set the excessive C/R limit value to
whatever you wish, so that the user will be logged out if
there are too many carriage returns sent to your system.
6.1.9 Show Status of Filenames -
This command shows you the current settings for some of
the filenames used by Metro-Mezzanine. Here is a sample:
Initial Menu Task filename:
MAIN
Welcome/Introduction Task filename:
WELCOME
Protocol List filename:
PROTOCOL
Customized Registration Screen filename:
REGINFO.ASC
Default command prompt:
[M-M IV]:
This will always display the latest information, so if you
change the data, it will be reflected in this status screen.
6.2 Setting up your BBS batch file -
This is a crucial step, because if this is improperly set up, your
system will not function well with Metro-Mezzanine. However, luckily,
this is an easy step, too.
Include the following paradigm in the BBS batch file that you use to
access your BBS's:
CD <Metro-Mezzanine directory>
MEZZ <DOOR info file>
If errorlevel <errorlevel value> goto <BBS routine>
If errorlevel <errorlevel value> goto <BBS routine>
If errorlevel <errorlevel value> goto <BBS routine>
If errorlevel <errorlevel value> goto <BBS routine>
If errorlevel <errorlevel value> goto <BBS routine>
.
. (repeat as many times as needed)
.
The "CD" command is used to switch the system focus into the Metro-
Mezzanine directory, so that the next line can work to activate
Metro-Mezzanine.
The second line, incidentally, will require a DOOR information
file... one of the following:
DOOR.SYS
DORINFO?.DEF
PCBOARD.SYS
or
GENERIC.SYS
If your mailer is capable of producing one of the first three DOOR
info files, then by all means, have it do so. If not, there are some
programs available which will be able to manufacture dummy DOOR info
files if given baud rate and comm port information. Or, you may take
one of the DOOR info files that your BBS program makes and modify it
to match different baud rates and/or comm ports, using your batch
file to copy the right file for use by Metro-Mezzanine. Or, even
more basic would be to use GENERIC.SYS to run Metro-Mezzanine. Let's
explore these options...
6.2.1 Mailer capable of making DOOR information file -
This is the simplest option: just have the mailer
manufacture of the first three listed DOOR info files, and
you're all set.
6.2.2 Dummy DOOR information file generation program -
This is a good method, too. Make sure that you inform this
program as to what the baud rate and comm port assignments
are.
Here is an example of the BBS batch file portion used to
impart information to Metro-Mezzanine using one of these
dummy generators:
CD H:\FD\MEZZ
MakDRSYS 2400 COM2:
MEZZ DOOR.SYS
.
.
.
6.2.3 Copying over DOOR information files -
You can grab a DOOR info file used by your BBS (these are
rarely deleted whenever a user returns from a DOOR) and take
a look inside it. Go ahead and modify it to match the
different baud rates and/or comm ports used by your BBS.
For instance, you run a 2400-9600 baud system (okay, it
comes to two basic baud rates... 2400 and 9600) on COM1:. So
you grab yourself a copy of DOOR.SYS that your BBS makes for
some DOORs. You change the baud rate line to reflect 2400
baud, then save to another name (D2400.SYS). You do the same
thing for 9600 baud (saved to D9600.SYS). Since the DOOR
info file already had correct comm port assignment (COM1:),
you did not have to change that.
The following is a BBS batch file portion which uses this
method. It assumes that the baud rate is being passed to it
from the mailer directly or the mailer batch file.
CD \FD\MEZZ
If %1==2400 copy D2400.SYS DOOR.SYS
If %1==9600 copy D9600.SYS DOOR.SYS
Mezz DOOR.SYS
.
.
.
6.2.4 GENERIC.SYS -
This is a special text file used by Metro-Mezzanine in lieu
of the other methods mentioned above. It contains three
lines:
line 1 - <sysop name>
line 2 - comm port
line 3 - time allowed (in minutes) in M-M
A sample GENERIC.SYS might read:
Steve
COM2:
60
The following is a sample BBS batch file portion which uses
the GENERIC.SYS file:
CD \BT\MEZZ
Mezz GENERIC.SYS
.
.
.
Frankly, this method is the preferred one at DevPalMiami
because FrontDoor cannot self-generate any DOOR information
files, and we would rather not have to spend time copying
over DOOR information files from elsewhere. Also,
GENERIC.SYS gives us more control over Metro-Mezzanine
access, making it even for everybody. If you do not know
which method of configuring Metro-Mezzanine (a DOOR
information file from your mailer, a copied-over DOOR
information file, or GENERIC.SYS), it is suggested that you
use GENERIC.SYS.
WARNING: Keep the time allowed under 250 minutes!
6.2.5 About errorlevels -
The following line:
If errorlevel <errorlevel value> goto <BBS routine>
can be used as many times as needed. The <errorlevel value>
holds whatever errorlevel you specified in MezSetup (see
Section 7.0 for information concerning errorlevel usage in
the Tasks), while the <BBS routine> is the batch label that
is accessed because of that errorlevel. Be careful to make
sure that the errorlevels are properly matched to their
corresponding labels.
6.3 Non-standard communications port support -
Section 6.2 explains how to set up Metro-Mezzanine using a vanilla
setup, which works perfectly for most people. However, for the
exceptions who, for some strange reason, need (or want) to use a
non-standard serial communications port to handle the interface
between the modem and the computer, here is the paradigm to do so:
MEZZ <DOOR info file> PORT:<port address>:<port number>
The <DOOR info file> parameter is for the complete path and filename
of the DOOR info file desired for use. The <port address> is the
actual base memory address for the serial port. The <port number> is
the integer of the serial port which you wish to use for the BBS
carousel.
For instance:
MEZZ h:\fd\mezz\generic.sys PORT:03F8:5
This means that Metro-Mezzanine is using the GENERIC.SYS file for
getting pertinent information from the BBS, and the non-standard
comm port is accessed at memory location 03F8, and the comm port
is known as COM5:.
Check the documentation for the non-standard serial port you intend
to use for the correct way to install that serial port on your
system.
6.4 DigiBoard support -
Section 6.2 explains how to set up Metro-Mezzanine using a vanilla
setup, which works perfectly for most people. However, for the
exceptions who, for some strange reason, need (or want) to use a
DigiBoard to handle the interface between the modem and the
computer, here is the paradigm to do so:
MEZZ <DOOR info file> PORT:D:<port number>
The <DOOR info file> parameter is for the complete path and filename
of the DOOR info file desired for use. The <port address> is the
actual base memory address for the serial port. The <port number> is
the integer of the serial port which you wish to use for the DOOR.
For instance:
MEZZ g:\bt\mezz\pcboard.sys PORT:D:4
This means that Metro-Mezzanine is using the PCBOARD.SYS file for
getting pertinent information from the BBS, and the DigiBoard
channel being used for Metro-Mezzanine is #4.
Check the DigiBoard documentation for the correct way to install
it and to use it on your system.
-----------------------------------------------------------------------------
7.0 TASK MANAGEMENT
Managing your Tasks with proficiency will allow you to muse about the
aesthetics in life rather than worry about the mud-and-sticks mechanics of
Metro-Mezzanine. Therefore, it is a good idea to make sure you understand
all of the concepts presented in this section of this document.
Once again, unregistered users are unencumbered by the extra features
available to registered users. These features will be marked by "{+}".
Unregistered users are also warned to NOT delete the WELCOME and MAIN Tasks.
When designing their systems, they should use the following filenames for
their screens:
WELCOME.ASC/ANS - Welcome/news text file
MAIN.ASC/ANS - Main menu text file
7.1 Task Keys -
A "Task Key" is both the command used in Metro-Mezzanine to invoke a
Task AND is also the filename used for the Task's data filename
(excluding the .TSK suffix)... remember the filenames for the Tasks?
So, if you create a Task called "HELP", when the user types HELP in
Metro-Mezzanine, it will access the HELP Task.
7.2 Task Types -
Before we discuss the commands available in the Task management part
of MezSetup, we need to discuss what types of different Tasks can be
designed within MezSetup.
As mentioned before, Tasks are commands that you create to tell
Metro-Mezzanine to do certain things. Therefore, it makes sense to
offer different Task Types to allow you to do those things in
Metro-Mezzanine.
Here is a summary of the Task Types available in Metro-Mezzanine
Type IV:
0 - keep the Task INACTIVE
1 - exit with errorlevel
2 - flash text file, then exit with errorlevel {+}
3 - flash text file {+}
4 - flash text file, then hit <RETURN> {+}
5 - download file via DSZ {+}
6 - flash text file, confirm for exiting with errorlevel,
then either exit with errorlevel or abort execution {+}
7 - flash text file, confirm for downloading a file with
DSZ, then either download file with DSZ or abort
execution {+}
8 - go to another Menu Task {+}
9 - flash bulletin menu text file, then accept input for a
specific bulletin {+}
Let us explore each of these tasks...
7.2.1 Type 0 -
REQUIRED set/edit:
[B] Task Type
Optional set/edit:
[A] Task Name
Type 0 is the default when the Task is first created. Type 0
is a null item: it makes the Task inactive so that a user
cannot do anything if they type in the Task key at the
Metro-Mezzanine command prompt.
7.2.2 Type 1 -
REQUIRED set/edit:
[B] Task Type
[C] Exits on Errorlevel
OPTIONAL set/edit:
[A] Task Name
[H] Exiting String {+}
[I] Task Password {+}
Type 1 is a standard exit with an errorlevel. When a user
access a Task of this type, Metro-Mezzanine will exit with
an errorlevel, and that errorlevel will lead to the
appropriate label, as specified in your batch file (see
Section 6.2 and Section 6.2.5). It can also be used to log
out of your system, assuming that the errorlevel specified
for the Task will match an errorlevel in your BBS batch file
that leads back to your front-end/mailer.
7.2.3 Type 2 -
REQUIRED set/edit:
[B] Task Type
[C] Exits on Errorlevel
[D] Text File Name {+}
[K] ANSI/ASCII Toggle {+}
[L] Display Pause {+}
OPTIONAL set/edit:
[A] Task Name
[I] Task Password {+}
Type 2 consists of displaying a text file to the user,
followed by exiting with an errorlevel. This option is good
to use if you want your users to read some information prior
to accessing a BBS program (or logging out, or accessing
another utility, etc.).
7.2.4 Type 3 -
REQUIRED set/edit:
[B] Task Type
[D] Text File Name {+}
[K] ANSI/ASCII Toggle {+}
[L] Display Pause {+}
OPTIONAL set/edit:
[A] Task Name
[I] Task Password {+}
Type 3 is a standard text file display. It will display a
text file that you specify for that Task. Note that after
displaying the text file, there is no pause or request that
the user hit the <RETURN> key to continue. So if you have a
Menu Task specified with a long menu screen, you might want
to select Type 4 to show your text file instead.
7.2.5 Type 4 -
REQUIRED set/edit:
[B] Task Type
[D] Text File Name {+}
[K] ANSI/ASCII Toggle {+}
[L] Display Pause {+}
OPTIONAL set/edit:
[A] Task Name
[I] Task Password {+}
Type 4 is just like Type 3, except that it asks the user to
hit the <RETURN> key after the text file is displayed, in
order to continue.
7.2.6 Type 5 -
REQUIRED set/edit:
[B] Task Type
[E] Download File Name {+}
OPTIONAL set/edit:
[A] Task Name
[I] Task Password {+}
Type 5 is a file download option. The filename is specified
by you for that Task. You MUST have DSZ available, either in
the Metro-Mezzanine directory or somewhere along the DOS
PATH, in order for this to function properly.
7.2.7 Type 6 -
REQUIRED set/edit:
[B] Task Type
[C] Exits on Errorlevel
[D] Text File Name {+}
[K] ANSI/ASCII Toggle {+}
[L] Display Pause {+}
OPTIONAL set/edit:
[A] Task Name
[H] Exiting String {+}
[I] Task Password {+}
Type 6 is similar to Type 2, in that the user is first shown
a text file and then later has the opportunity to exit with
an errorlevel. However, in between those two processes, the
user is asked if he/she WANTS to exit Metro-Mezzanine with
that errorlevel. Thus, this is a perfect Task Type to use
for New User Logins or for regular BBS Logins where you want
the user to read about the BBS that he/she is about to enter
and then allow him/her to decide if he/she really wants to
access that BBS, or instead go back and make another
selection within Metro-Mezzanine.
7.2.8 Type 7 -
REQUIRED set/edit:
[B] Task Type
[D] Text File Name {+}
[E] Download File Name {+}
[K] ANSI/ASCII Toggle {+}
[L] Display Pause {+}
OPTIONAL set/edit:
[A] Task Name
[I] Task Password {+}
Like Type 6, Type 7 shows the user a text file and then
queries the user about whether he/she would like to do
something. In this case, however, instead of exiting with an
errorlevel, the user must decide whether to download a file
or not.
If the user decides that, yes, he/she would like to
download the prescribed file, the protocol selection menu
will be displayed (requiring the user's choice of transfer
protocol to continue) and then the file downloading process
will begin.
If the user decides to NOT download the file, he/she
is merely returned back to the current menu in Metro-
Mezzanine.
7.2.9. Type 8 -
REQUIRED set/edit:
[B] Task Type
[F] Menu File Name {+}
[K] ANSI/ASCII Toggle {+}
[L] Display Pause {+}
OPTIONAL set/edit:
[A] Task Name
[I] Task Password {+}
[J] Menu Prompt {+}
This is a very important Task Type: the Menu Task Type.
With this Task Type, you can designate the current menu to
display to the user.
In Section 6.1.4 (for registered users), you
specified a new Task for the Initial Menu Task or merely
left the default as-is. In either case, that Initial Menu
Task tells Metro-Mezzanine to display the prescribed text
file to the user as a menu screen. Thereafter, if the user
accesses a Type 8 Task (a Menu Task), he/she is displayed
the new menu screen associated with that Menu Task until,
once again, he/she accesses another Menu Task. In this way,
the current menu is always shown.
7.2.9.1 Super-global-humongous-power jumping -
As you may have noticed, every Task has a unique
key... there cannot be two J.TSK files (for a "J"
command). Is this significant?
YES! There is a special feature in Metro-Mezzanine
that allows users to type in a command that exists
ANYWHERE in Metro-Mezzanine and immediately access
that Task, instead of wading through any number of
menu screens that you may have designed. This is the
DevExpressWay(tm) feature.
DevExpressWay(tm) is especially good for
callers who use scripts to access your metronet: if
they are long distance callers, and they need to
access your system to fetch .QWK mail for their own
system, for instance, being able to quickly access
the appropriate Task without wasting time on the
menu screens. Also, it cuts down dramatically on the
complexity of such automated scripts, reducing the
room for error and even higher phone bills (as the
caller attempts to figure out what went wrong and to
fix it).
It is up to you to decide whether to inform your
users about the DevExpressWay(tm) feature or not. I
personally believe it to be a very important and
useful feature that all users should be aware of.
7.2.10 Type 9 -
REQUIRED set/edit:
[B] Task Type
[D] Text File Name {+}
[G] Bulletin Common Name {+}
[K] ANSI/ASCII Toggle {+}
[L] Display Pause {+}
OPTIONAL set/edit:
[A] Task Name
[I] Task Password {+}
[J] Menu Prompt {+}
Type 9 is a new feature to Metro-Mezzanine Type IV: it
allows you to set up a bulletin menu subsystem, very much in
the same manner as those appearing on full-blown BBS
packages.
You need to specify the text filename to be used as
a selection menu for the bulletins, and then you need to
specify the generic filename for all of the bulletin text
files.
What exactly is the generic filename for the bulletin text
files? The filename specifier itself SHOULD be less than
eight characters long (the shorter the better), but the path
specifier can point to any legitimate storage space on your
system, ie. even if your Metro-Mezzanine setup is located in
H:\MEZZ, you can use D:\BLTS\INFO as the generic filename
for the bulletin text files.
Using the example above, INFO is the filename
specifier. With this specifier, you can have the filenames
fit the following paradigm:
INFOxxxx.ggg
where "xxxx" are any four alphanumeric characters and any
other characters which are valid in a DOS filename, and
"ggg" is either .ASC (for an ASCII file) or .ANS (for ANSI).
In your bulletin selection menu file, you will list all of
the keys to access the bulletin files, namely those very
same xxxx parameters that you used in the bulletin
filenames. It's that simple! (Many of you probably have
experience with QuickBBS, RemoteAccess, PCBoard, and other
BBS programs employing similar methods for bulletin menu
displaying, so this should not be a shock to you!)
7.3 Task Information Display -
When you create a new Task or edit an existing one, you are shown
a screen which resembles the following:
Task DATA\welcome.TSK Information
[A] Task Name : Welcome/News Screen
[B] Task Type : 3
[C] Exits on Errorlevel : 255
[D] Text File Name :
welcome
[E] Download File Name :
NONE
[F] Menu File Name :
MAIN
[G] Bulletin Common Name :
NONE
[H] Exiting String :
Accessing...
[I] Task Password : NONE
[J] Menu Prompt : [M-M IV]:
[K] ANSI/ASCII Toggle : ANSI+ASCII
[L] Display Pause : Yes
[Q]UIT
Edit which? :
The above is the screen displayed for the default WELCOME Task.
Obviously, the information shown will vary with each Task, and there
is also a default set used whenever you create a new Task.
Here is a summary of the options available when editing a Task:
[A] Task Name
[B] Task Type
[C] Exits on Errorlevel
[D] Text File Name {+}
[E] Download File Name {+}
[F] Menu File Name {+}
[G] Bulletin Common Name {+}
[H] Exiting String {+}
[I] Task Password {+}
[J] Menu Prompt {+}
[K] ANSI/ASCII Toggle {+}
[L] Display Pause {+}
[Q]UIT
Here is a detailed discussion concerning these editing options:
7.3.1 Task Name -
=-= Optional =-=
You can give the Task a description so that it will be
listed with the useful information whenever you flip through
the list of existing Tasks in your Metro-Mezzanine setup
when you pick the option to add/edit/delete Tasks within
MezSetup.
7.3.2 Task Type -
=-= For all Tasks =-=
The Task Type is the specifier you issue to Metro-Mezzanine
so it understands exactly what to do when a user types in
the command for that Task. See Section 7.2 about Task Types.
The WELCOME and MAIN Tasks are special reserved Tasks, so
unregistered users should NOT change the Task Type for the
WELCOME or MAIN Tasks!
7.3.3 Exits on Errorlevel -
=-= For Task Types: 1, 2, 6 =-=
For those Task Types which require an errorlevel, this is
where you have the opportunity to enter it. This is the
errorlevel value that you must check for in your BBS batch
file that runs Metro-Mezzanine. See Section 6.2 for more
details on this.
Note that you cannot assign any errorlevels between 1 and 9
inclusive, but 0 is a valid choice.
7.3.4 Text File Name {+} -
=-= For Task Types: 2, 3, 4, 6, 7, 9 =-=
This allows you to set the filename needed for displaying
text files within Task Types that use this information.
Remember that you can supply both ASCII and ANSI
equivalents.
7.3.5 Download File Name {+} -
=-= For Task Types: 5, 7 =-=
This allows you to set the filename which specifies the file
that you wish the user to download.
7.3.6 Menu File Name {+} -
=-= For Task Types: 8 =-=
The menu file is actually an ASCII/ANSI text file that you
get to specify as the menu screen for a Menu Task. See
Section 7.2.9 for more information about Menu Tasks.
7.3.7 Bulletin Common Name {+} -
=-= For Task Types: 9 =-=
When using a Bulletin Task, this is where you have the
opportunity to enter the generic file specifier for the
bulletin files. See Section 7.2.10 for more information
about Bulletin Tasks.
7.3.8 Exiting String {+} -
=-= For Task Types: 1, 2, 6 =-=
Generally speaking, this option is also considered whenever
a Task allows for exiting Metro-Mezzanine with an
errorlevel. This a one-line text string that you can have
displayed to the callers. This is especially useful as an
introductory sentence that prepares the caller for the
transition from Metro-Mezzanine to the program that you have
specified in your BBS batch file.
7.3.9 Task Password {+} -
=-= For Task Types: 1, 2, 3, 4, 5, 6, 7, 8, 9 =-=
The ability to safeguard Tasks with security passwords
enables you to provide services to some callers and not to
others. You can disciminate between regular callers and
other BBS's calling in to perform .QWK mail transfers, for
instance. Or, if you are a software developer and need your
beta testers to access a secure BBS partition that you have
set up, you can use this feature to prevent unwanted callers
from making a mess of everything. Also, you can have special
text file displays protected with passwords for the eyes of
certain people only. A very useful feature which I highly
recommend for the security-minded.
7.3.10 Menu Prompt {+} -
=-= For Task Types: 8, 9 =-=
This allows you to specify individual customized command
prompts at the various Menu and Bulletin Tasks that you
create.
7.3.11 ANSI/ASCII Toggle {+} -
=-= For Task Types: 2, 3, 4, 6, 7, 9 =-=
Use this to toggle between detection for ASCII text files
only, or for both ANSI and ASCII file availability.
If a caller decides that he/she wishes to see ANSI
and your system supports it, then having this toggle set for
ASCII+ANSI will allow him/her to see your .ANS files if they
are available in the Tasks that you have created.
7.3.12 Display Pause {+} -
=-= For Task Types: 2, 3, 4, 6, 7, 9 =-=
If you include long text files in your Tasks, and if you
wish to have your callers see all of them without having a
coronary attack from attempting to keep up with warp-speed
text scrolling (in the case of 9600+ setups), then setting
this toggle to YES will solve that dilemma.
NOTE: if you are using extensive ANSI screens, then make
sure this is set to NO unless you claim to know what you are
doing.
7.4 Note About Extraneous Information -
If you enter information for a Task that the Task does not use, that
information is just ignored. For instance, if you entered an
errorlevel and a filename for a Type 1 Task, you know that the
filename will be ignored because Type 1 Tasks are standard exits
using an errorlevel. However, if you neglect to enter an errorlevel,
your setup may act "funny". On the other hand, you may have
deliberately entered the filename for the Type 1, with the purpose
of later changing the Task from a Type 1 Task to a Type 2 task,
which DOES use the filename to display a text file to the user.
-----------------------------------------------------------------------------
8.0 PRODUCT SUPPORT
To maintain his position as one of the most accessible shareware author, the
information following has been provided:
Address: Steven H. Lin, Ph.D., M.S.
DevPal MetroNet Communications
1251 NE 108th St., #621
Miami, FL 33161
BBS: [The Deviant's Palace] of Miami
305/899-1841
2400-14.4k HST/v.32bis
24 hours except ZMH
Voice: 305/899-0957
FN NetMail: FN 1:135/105.0
EN 50:5305/505.0
DN 55:55/1.0
DR 75:75/1.0
Internet: slinc@f135.n105.z1.fidonet.org
FN EchoMail: AOTD - DevOnline Products echo [DN/DR/FN]
DEV_SYSOP - DevNet Systems Operations echo [DN/FN]
DEV_TPA - Third Party Apps Developers echo [DN/FN]
DOORGAMES - DOOR Games Discussions echo [FN]
DOORWARE - DOORware echo [RN/FN]
D_UTIL - DOOR Utilities echo [DR]
PCBNET - PCBoard Sysops echo [FN]
RA_UTIL - RemoteAccess Utilities echo [FN]
U'NI-net/US: DOOR-UTIL - DOORs and utilities for BBS's
VirtualNet: 1 @3053
2 @3053
Voice support is given freely and is the preferred method of communication
by the author. Please take advantage of this remarkable avenue of support.
To further expand accessibility, there are now official DevOnline
distribution sites available to provide you with the latest unregistered
versions of DevOnline products:
DevOnCO (Mountain US) : The Hornet's Nest
sysop: Kevin Higgins loc: Fort Carson, CO
#: 719/579-0593 baud: 2400-14.4k HST
ice: TAG
addr: FN 1:128/74.0, VN 45:521/101.0
PCP: n/a
DevOnFL (Eastern US) : [The Deviant's Palace] of Miami
sysop: Steve Lin loc: Miami, FL
#: 305/899-1841 baud: 2400-14.4k HST/v.32bis
ice: Maximus-CBCS, PCBoard, QuickBBS, RemoteAccess,
WWIV-IMS, Virtual BBS, Waffle/DOS
addr: FN 1:135/105.0, EN 50:5305/505.0, DN 55:55/1.0,
UN DEVPAL, VtN @3053
PCP: FLMIA
DevOnTX (Southern US) : The Chess Board
sysop: Ken Givens loc: Grand Prairie, TX
#: 214/641-1136 baud: 2400-14.4k HST
ice: SuperBBS
addr: FN 1:1/132.0, FN 1:124/2213.0, 43:1370/101.0
PCP: TXDAL
DevOnVA (Mid-Atlantic US) : The NEOCOM Game Connection
sysop: David Fife loc: Martinsville, VA
#: 703/638-1952 baud: 2400-14.4k HST/9600 v.32
ice: RemoteAccess
addr: FN 1:264/615.0, DR 75:100/1.0
PCP: n/a
-----------------------------------------------------------------------------
9.0 ACKNOWLEDGEMENTS
All products mentioned in this text that are not produced by members of
DevPal MetroNet Communications, Inc. are trademarks of their respective
copyright holders and/or authors.
9.1 Dedication -
This program is dedicated to Wuu Shyong Lin, for having struggled so
long against insurmountable odds for his entire life and for
sacrificing everything he possessed and everything he was for his
family. Rest gracefully in peace.
9.2 And special thanks to (in alphabetical order)...
Michael Altschul, Ph.D. Rickie Belitz & DCIS
Cam N. DeBuck Gene de Libero
Ken Givens & The Chess Board Bonnie Hartstein & DevPalAnA
Corinna Harney & DevPalLV Norm Henke & PC-OHIO
John Hicks Kevin Higgins & The Hornet's Nest
Sil Horwitz Bruce Ikenaga, Ph.D.
Elaine Irwin Mary Lambert
Bob Mahoney & EXEC-PC Fred Maximilien
Omen Technology, Inc. PKWARE, Inc.
Herb Ritts
Mike Stewart, Ph.D., M.S. & DPBerk
John Theed Alejandra Torriano & DevPalDC
Ian Wells & TSanc Kari Wuhrer
... and to all of the very special sysops who picked up a copy of
Metro-Mezzanine
9.3 Product Acknowledgements -
PCBoard, by Clark Development Company
QuickBBS, by Steve Gabrilowitz and Richard Creighton
RemoteAccess, by Andrew Milner
-----------------------------------------------------------------------------
10.0 FINAL WORDS
Metro-Mezzanine has a long way to go, in my opinion. It is not actually one
product, but rather a series of similar products geared toward facilitating
the access of BBS programs. No longer is a BBS program by itself considered
enough. Today's BBS's must have utility programs which enhance the its
performance many times over. Metro-Mezzanine fills a gap in an area which
has very few other comparable utilities; and Metro-Mezzanine, unlike its
competitors, is versatile and flexible enough to be used in more than a
single role. Until the advent of Metro-Mezzanine, there were generally
considered to be only EIGHT programs which acted as BBS carousels. One of
them was Ghostwheel and thus unavailable to the public and, anyways, it was
over three megabytes in size and required the concurrent setup of MS-DOS and
UNIX/386; two others were not actually programs... they were clever but
difficult-to-manage and problematic ways to manipulate batch files and
certainly not very comfortable nor reliable for sysops; another was a way
of fooling a certain mailer's own external mail routines to think the
incoming caller was a mail run, and thus offered very little in the way of
amenities or security; two were actually optional menus configured into BBS
programs but were not robust enough to handle all callers faultlessly and
were not flexible enough to be used to handle situations except as user
screening devices; the author of another disappeared a short time after
his product was released; and the last one was extremely overpriced for
the limited features it offered and its author also vanished abruptly.
Metro-Mezzanine represents the first true attempt to provide a versatile
pre-BBS and/or inter-BBS interface robust enough for handling many
different situations.
Feel free to experiment. Metro-Mezzanine was not developed for sysops who
like to have bland, monotonous systems: it was meant for the enterprising,
inspired sysops who believe that they have something special to offer to
others. It is the pioneering spirit of Modemland that Metro-Mezzanine caters
to, not the evils of stagnation.
Happy designing!
- Steven H. Lin, Ph.D., M.S.
-----------------------------------------------------------------------------
METRO-MEZZANINE, Type IV
Registration Form 4E - Version 4.31
DevOnline Product MEZZ-X4
Sysop Name _________________________________________________________________
BBS Name ___________________________________________________________________
BBS Phone Number ___________________________________________________________
BBS City, State ____________________________________________________________
Sysop's Address ____________________________________________________________
(no P.O. Boxes) ____________________________________________________________
____________________________________________________________
Sysop's Voice Phone Number(s) ______________________________________________
____________________________________________________________________________
Any Mail Network Addresses _________________________________________________
____________________________________________________________________________
Indicate which registration option(s) you'd like by CIRCLING the correct
number(s) below:
#1 - Non-commercial registration [$20.00 US]
#2 - Commercial registration [$35.00 US]
#3 - Normal USER status on DevPal [FREE] \
#4 - One year standard registration on DevPal [$8.00] > pick one
#5 - One year preferred registration on DevPal [$12.00] /
#6 - Consideration for beta test site [FREE]
#7 - USPS mail delivery of disk (see below) [$5.00] OPTIONAL
Total cost: ___________________________
Your System Hardware (be specific!)_________________________________________
____________________________________________________________________________
____________________________________________________________________________
____________________________________________________________________________
Your BBS Software (be specific!)____________________________________________
____________________________________________________________________________
Registered Key Delivery: _____ via File Attach (a la FidoNet)
_____ I prefer maximum security... Hold my copy on
DevPalMiami so I can d/l it myself. Name the
M-M reg. key file __________________________
and encrypt it with the password ___________
and put the file in the DevOnline file area
on NightVeil PCBoard BBS partition!
_____ Send my copy to me by mail. I understand
that I will pay US $5.00 for S&H if I am in
the U.S. and US $10.00 for S&H if I am out-
side the U.S.
Signature ___________________________________ Birthdate ____________________